Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e52ccf1feb338b20bbd73073a46f10111ccca04ced160c3a63ba2732fadad664

Tx prefix hash: e8d03186ad6dd1eb398049d1ad9b2da74f8f003b6dc5733366d459f716b42544
Tx public key: 60201974957bf8f39e9a72915d96c9131f3cc3a88c9ff6b87cb253430ca9caa3
Timestamp: 1672718071 Timestamp [UCT]: 2023-01-03 03:54:31 Age [y:d:h:m:s]: 02:164:09:03:10
Block: 666431 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 639111 RingCT/type: yes/0
Extra: 0160201974957bf8f39e9a72915d96c9131f3cc3a88c9ff6b87cb253430ca9caa302110000000152542ceb000000000000000000

1 output(s) for total of 3.800470894000 dcy

stealth address amount amount idx
00: 549afa0ec664827f4c34e2a05c84db499f51a24ab5eab5f223903dfba6f7b2b0 3.800470894000 1107542 of 0

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": 666441, "vin": [ { "gen": { "height": 666431 } } ], "vout": [ { "amount": 3800470894, "target": { "key": "549afa0ec664827f4c34e2a05c84db499f51a24ab5eab5f223903dfba6f7b2b0" } } ], "extra": [ 1, 96, 32, 25, 116, 149, 123, 248, 243, 158, 154, 114, 145, 93, 150, 201, 19, 31, 60, 195, 168, 140, 159, 246, 184, 124, 178, 83, 67, 12, 169, 202, 163, 2, 17, 0, 0, 0, 1, 82, 84, 44, 235, 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