Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4c81cfe5aa4d796d9e93753e1a2e0c2436b24f7f22d1c43d2ad2d586a7610631

Tx prefix hash: 5c370b5713574df9b2af6cfa704d7e17094893e247bd75727adc199d5a7334ea
Tx public key: bbebf5e67eb55682ddc28ebd4724a861f60345f40a43045e218b0ecafe91e13d
Timestamp: 1707964992 Timestamp [UCT]: 2024-02-15 02:43:12 Age [y:d:h:m:s]: 01:029:12:14:22
Block: 957770 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 282147 RingCT/type: yes/0
Extra: 01bbebf5e67eb55682ddc28ebd4724a861f60345f40a43045e218b0ecafe91e13d0211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2ffa5444794227c25e0b146621dc82e28b47c16af31adfb02d8ec4553d27abaa 0.600000000000 1417119 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": 957780, "vin": [ { "gen": { "height": 957770 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2ffa5444794227c25e0b146621dc82e28b47c16af31adfb02d8ec4553d27abaa" } } ], "extra": [ 1, 187, 235, 245, 230, 126, 181, 86, 130, 221, 194, 142, 189, 71, 36, 168, 97, 246, 3, 69, 244, 10, 67, 4, 94, 33, 139, 14, 202, 254, 145, 225, 61, 2, 17, 0, 0, 0, 1, 122, 156, 244, 199, 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