Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 413a654f8d0974f517ea3dd9299fc6fffa5bc1f93b55014a671c7a450c797dcc

Tx prefix hash: df3e550a819fdb877e3e3741fe04fe82f88ea6e7881bf0790b9b7341288cd390
Tx public key: 8050ce3b674e30d6d785ef9b374acc4d1c2216effc0b7258591dc0efce03861e
Timestamp: 1712036822 Timestamp [UCT]: 2024-04-02 05:47:02 Age [y:d:h:m:s]: 01:004:20:06:41
Block: 991505 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 264434 RingCT/type: yes/0
Extra: 018050ce3b674e30d6d785ef9b374acc4d1c2216effc0b7258591dc0efce03861e02110000000352d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4e3d35af336e8aaa07e08bc13168145be9c4f1ec557808503e3b07d5e1f2aa51 0.600000000000 1451841 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": 991515, "vin": [ { "gen": { "height": 991505 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4e3d35af336e8aaa07e08bc13168145be9c4f1ec557808503e3b07d5e1f2aa51" } } ], "extra": [ 1, 128, 80, 206, 59, 103, 78, 48, 214, 215, 133, 239, 155, 55, 74, 204, 77, 28, 34, 22, 239, 252, 11, 114, 88, 89, 29, 192, 239, 206, 3, 134, 30, 2, 17, 0, 0, 0, 3, 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