Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2dd708e7aee24de7df6cd6bb5480b6f9b12df6b3a6556c5b7b6a54a555e9cafd

Tx prefix hash: bdacefa233cef180604e7b7545cbf24681d5da5311b6a83b1909547c8908318e
Tx public key: 180288e7a3fa5e6fce48db173eb60aa8c3fa25ae03b985b258cd7ce37c3a0833
Timestamp: 1713192105 Timestamp [UCT]: 2024-04-15 14:41:45 Age [y:d:h:m:s]: 01:268:14:46:42
Block: 1001105 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 450730 RingCT/type: yes/0
Extra: 01180288e7a3fa5e6fce48db173eb60aa8c3fa25ae03b985b258cd7ce37c3a083302110000000659dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1b3b16da60dec912ff683da6a9f8971a82b939d0462917bead3947d829913b96 0.600000000000 1461607 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": 1001115, "vin": [ { "gen": { "height": 1001105 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1b3b16da60dec912ff683da6a9f8971a82b939d0462917bead3947d829913b96" } } ], "extra": [ 1, 24, 2, 136, 231, 163, 250, 94, 111, 206, 72, 219, 23, 62, 182, 10, 168, 195, 250, 37, 174, 3, 185, 133, 178, 88, 205, 124, 227, 124, 58, 8, 51, 2, 17, 0, 0, 0, 6, 89, 218, 211, 245, 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