Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9b947479bd51ad439aa4f332d6dc8eb34a6b153da3a5c04b33561632c3495dac

Tx prefix hash: 6b664de8d336a7dd849fbbc79757aae668632e2f45c367df2d603ab0a38f097b
Tx public key: 6c2fef041b18a9f5ae0f72a48f6d85ec3571152f6b731966f67b88529ebbfaf1
Timestamp: 1711788731 Timestamp [UCT]: 2024-03-30 08:52:11 Age [y:d:h:m:s]: 01:076:22:30:44
Block: 989506 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 315883 RingCT/type: yes/0
Extra: 016c2fef041b18a9f5ae0f72a48f6d85ec3571152f6b731966f67b88529ebbfaf102110000000452d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b57d7a5129ad0360c75cc2278ed94314153101136d52dee35c7e1ff7804be3b3 0.600000000000 1449805 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": 989516, "vin": [ { "gen": { "height": 989506 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b57d7a5129ad0360c75cc2278ed94314153101136d52dee35c7e1ff7804be3b3" } } ], "extra": [ 1, 108, 47, 239, 4, 27, 24, 169, 245, 174, 15, 114, 164, 143, 109, 133, 236, 53, 113, 21, 47, 107, 115, 25, 102, 246, 123, 136, 82, 158, 187, 250, 241, 2, 17, 0, 0, 0, 4, 82, 212, 126, 148, 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