Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 56e7ae6110784dfc5a477743dae47a0a091abc81ed70ba97c627ba29e97d86ce

Tx prefix hash: 707e6ff85dd0b335205b7e9f5ed6bfb0f0a02f5160919ddc1e783b8b5e5aa97b
Tx public key: c6c6c9fc3f490284c31f7ce380dd61e8be538cb7667720303877606640eec40b
Timestamp: 1648538275 Timestamp [UCT]: 2022-03-29 07:17:55 Age [y:d:h:m:s]: 03:030:07:33:16
Block: 468764 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 801888 RingCT/type: yes/0
Extra: 01c6c6c9fc3f490284c31f7ce380dd61e8be538cb7667720303877606640eec40b02110000000c4a0f5013000000000000000000

1 output(s) for total of 17.170799856000 dcy

stealth address amount amount idx
00: 0ad9b1790f85798acd3e381d678dcbdfb8aa00a4117d378e591d9b75a9735bc9 17.170799856000 887548 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": 468774, "vin": [ { "gen": { "height": 468764 } } ], "vout": [ { "amount": 17170799856, "target": { "key": "0ad9b1790f85798acd3e381d678dcbdfb8aa00a4117d378e591d9b75a9735bc9" } } ], "extra": [ 1, 198, 198, 201, 252, 63, 73, 2, 132, 195, 31, 124, 227, 128, 221, 97, 232, 190, 83, 140, 183, 102, 119, 32, 48, 56, 119, 96, 102, 64, 238, 196, 11, 2, 17, 0, 0, 0, 12, 74, 15, 80, 19, 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