Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2df2ad5d7a8686bfbfdd44b571d065f914abfc5be210bf4f7c7e40cb830f814a

Tx prefix hash: d1896fed3c9689f071449338454ff608700373ed9ad69bff97332c1199c44f4a
Tx public key: 276c9fd186073e9f67307284386d99c224c0c7ecaadd726d5e104022fddb5f0b
Timestamp: 1706582020 Timestamp [UCT]: 2024-01-30 02:33:40 Age [y:d:h:m:s]: 01:029:06:47:44
Block: 946287 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 281987 RingCT/type: yes/0
Extra: 01276c9fd186073e9f67307284386d99c224c0c7ecaadd726d5e104022fddb5f0b0211000000030011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 669fcf2472b3fa11eda6f0f4e5c056a04d2e1642332dcf2b6125d0ae00cd3784 0.600000000000 1404619 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": 946297, "vin": [ { "gen": { "height": 946287 } } ], "vout": [ { "amount": 600000000, "target": { "key": "669fcf2472b3fa11eda6f0f4e5c056a04d2e1642332dcf2b6125d0ae00cd3784" } } ], "extra": [ 1, 39, 108, 159, 209, 134, 7, 62, 159, 103, 48, 114, 132, 56, 109, 153, 194, 36, 192, 199, 236, 170, 221, 114, 109, 94, 16, 64, 34, 253, 219, 95, 11, 2, 17, 0, 0, 0, 3, 0, 17, 5, 91, 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