Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 89c5ec264a75f0b2881e01aa94bb8451e4e664279c1c937d07a8063d0a5b7b65

Tx prefix hash: 6da0dcaa229d2e1b93c4a2354940ad5be87113b9aaf91c10d049ed40829af651
Tx public key: fc646470aff5f574184b245b6312694f5d31c824b8f3974b18e4bf3b7006ca9b
Timestamp: 1579226331 Timestamp [UCT]: 2020-01-17 01:58:51 Age [y:d:h:m:s]: 04:294:13:20:38
Block: 47160 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1100011 RingCT/type: yes/0
Extra: 01fc646470aff5f574184b245b6312694f5d31c824b8f3974b18e4bf3b7006ca9b02110000000a8a2ee0d9000000000000000000

1 output(s) for total of 428.314404734000 dcy

stealth address amount amount idx
00: a9761bad9e664eda6c62e2e2f4c52267fc8b7f93f87602dd2f274c78a6eb7bb7 428.314404734000 87137 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": 47170, "vin": [ { "gen": { "height": 47160 } } ], "vout": [ { "amount": 428314404734, "target": { "key": "a9761bad9e664eda6c62e2e2f4c52267fc8b7f93f87602dd2f274c78a6eb7bb7" } } ], "extra": [ 1, 252, 100, 100, 112, 175, 245, 245, 116, 24, 75, 36, 91, 99, 18, 105, 79, 93, 49, 200, 36, 184, 243, 151, 75, 24, 228, 191, 59, 112, 6, 202, 155, 2, 17, 0, 0, 0, 10, 138, 46, 224, 217, 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