Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d790df5c4a9eed0c2b7fdb53c661c95a554874a153b21371736716ebefd215ba

Tx prefix hash: 15d81e270b509547aeaab8128bb9a2c81a1819b12eeba1ab5f150d5c0a36aac0
Tx public key: 97687a12c1b840baef39ddd3fcc01aa7fa7546ca9b1050d14e2fcbde2d492108
Timestamp: 1639460932 Timestamp [UCT]: 2021-12-14 05:48:52 Age [y:d:h:m:s]: 02:340:03:34:38
Block: 395132 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 761165 RingCT/type: yes/0
Extra: 0197687a12c1b840baef39ddd3fcc01aa7fa7546ca9b1050d14e2fcbde2d49210802110000000176899486000000000000000000

1 output(s) for total of 30.113692783000 dcy

stealth address amount amount idx
00: e5b5fb1cdd400fe9d96086b2ea63120da9793afc187d1a784b1b99de7f435d8d 30.113692783000 792949 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": 395142, "vin": [ { "gen": { "height": 395132 } } ], "vout": [ { "amount": 30113692783, "target": { "key": "e5b5fb1cdd400fe9d96086b2ea63120da9793afc187d1a784b1b99de7f435d8d" } } ], "extra": [ 1, 151, 104, 122, 18, 193, 184, 64, 186, 239, 57, 221, 211, 252, 192, 26, 167, 250, 117, 70, 202, 155, 16, 80, 209, 78, 47, 203, 222, 45, 73, 33, 8, 2, 17, 0, 0, 0, 1, 118, 137, 148, 134, 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