Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: 981ee1bdcf15b4cef5e60e0441c445c4e368d1a9e5d54f3d7760864e60787138

Tx prefix hash: e46785e096161a4c8baa63ea0c98f69d350c0531742da3337212c21ccd1ea824
Tx public key: 9987d543e13f6fdd937578109b0e7aa2303e79fd0ae4a361a0d22d90b3f81e96
Timestamp: 1724957774 Timestamp [UCT]: 2024-08-29 18:56:14 Age [y:d:h:m:s]: 00:269:08:34:31
Block: 1098655 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 192405 RingCT/type: yes/0
Extra: 019987d543e13f6fdd937578109b0e7aa2303e79fd0ae4a361a0d22d90b3f81e96021100000007e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0a273637dac95e70b239618b9af3cc4e70c8bd4b28199b81940c9551a25ba5b9 0.600000000000 1574446 of 15

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 1098665, "vin": [ { "gen": { "height": 1098655 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0a273637dac95e70b239618b9af3cc4e70c8bd4b28199b81940c9551a25ba5b9" } } ], "extra": [ 1, 153, 135, 213, 67, 225, 63, 111, 221, 147, 117, 120, 16, 155, 14, 122, 162, 48, 62, 121, 253, 10, 228, 163, 97, 160, 210, 45, 144, 179, 248, 30, 150, 2, 17, 0, 0, 0, 7, 233, 20, 221, 21, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8