Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3e5c31909cf395d41c7224ae9183cb99175496a30b3cb7641f0fa9ccda80898c

Tx prefix hash: 6ca52dd92445b57072dd954cd7b226fe8c2e2731ce14e5f431039412de3e9d3f
Tx public key: 4fbb4bb8df6ed9bd6a5218e94fa6c449c0b238274d1fcbb13db68ef7f510d471
Timestamp: 1715112476 Timestamp [UCT]: 2024-05-07 20:07:56 Age [y:d:h:m:s]: 01:008:11:41:44
Block: 1017039 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 266982 RingCT/type: yes/0
Extra: 014fbb4bb8df6ed9bd6a5218e94fa6c449c0b238274d1fcbb13db68ef7f510d4710211000000047a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1c391d7a6c23612af73b4d03a4914d496bf36c150542cf69659e765986318bee 0.600000000000 1480798 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": 1017049, "vin": [ { "gen": { "height": 1017039 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1c391d7a6c23612af73b4d03a4914d496bf36c150542cf69659e765986318bee" } } ], "extra": [ 1, 79, 187, 75, 184, 223, 110, 217, 189, 106, 82, 24, 233, 79, 166, 196, 73, 192, 178, 56, 39, 77, 31, 203, 177, 61, 182, 142, 247, 245, 16, 212, 113, 2, 17, 0, 0, 0, 4, 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