Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7e95e69ef84ba7ca935686487a43742c5bb818abbdabae75c766b44520752417

Tx prefix hash: 461ad338c6c156e6a3d61bd6d70112c8d6cba6bb50ccdb1127c0d763587480f5
Tx public key: 9f7b97ad411c24ce7e6174751ff341076656aa1c4b7a3c8b3f48315c7b1a0b97
Timestamp: 1648517094 Timestamp [UCT]: 2022-03-29 01:24:54 Age [y:d:h:m:s]: 02:316:10:16:30
Block: 468587 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 745465 RingCT/type: yes/0
Extra: 019f7b97ad411c24ce7e6174751ff341076656aa1c4b7a3c8b3f48315c7b1a0b9702110000000406faf294000000000000000000

1 output(s) for total of 17.194003105000 dcy

stealth address amount amount idx
00: c1bdff63e79b90a3912bc12a879105c263281baeb98d6452e3d5c404655cbf6d 17.194003105000 887333 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": 468597, "vin": [ { "gen": { "height": 468587 } } ], "vout": [ { "amount": 17194003105, "target": { "key": "c1bdff63e79b90a3912bc12a879105c263281baeb98d6452e3d5c404655cbf6d" } } ], "extra": [ 1, 159, 123, 151, 173, 65, 28, 36, 206, 126, 97, 116, 117, 31, 243, 65, 7, 102, 86, 170, 28, 75, 122, 60, 139, 63, 72, 49, 92, 123, 26, 11, 151, 2, 17, 0, 0, 0, 4, 6, 250, 242, 148, 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