Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e0664e6a049e753d2fbc9999976718af7ca0d27ba61346d95d5589397cd862b9

Tx prefix hash: a0d06de6940b4423db25dae354cf7f8f10b8e913f84f635a635ec0ab7d4d5a90
Tx public key: c2bee0d0bbe64c6d674fd29a1a7617f0830f436eec3adc9c609554c5e7e99b2d
Timestamp: 1727765844 Timestamp [UCT]: 2024-10-01 06:57:24 Age [y:d:h:m:s]: 00:178:02:51:37
Block: 1121943 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 127091 RingCT/type: yes/0
Extra: 01c2bee0d0bbe64c6d674fd29a1a7617f0830f436eec3adc9c609554c5e7e99b2d021100000004e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b236ff9adb0aef264bbdda55df1477f4f26b4e14ecefd34dc0296d877b59f4b0 0.600000000000 1604306 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": 1121953, "vin": [ { "gen": { "height": 1121943 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b236ff9adb0aef264bbdda55df1477f4f26b4e14ecefd34dc0296d877b59f4b0" } } ], "extra": [ 1, 194, 190, 224, 208, 187, 230, 76, 109, 103, 79, 210, 154, 26, 118, 23, 240, 131, 15, 67, 110, 236, 58, 220, 156, 96, 149, 84, 197, 231, 233, 155, 45, 2, 17, 0, 0, 0, 4, 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