Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5e231edea2e05fe68d525f0385a9ea9b3648b854bf687fecd070d45a53db0e45

Tx prefix hash: 54aac13dace7b12aa6d5436306249d3b6f491ad3bca42c55f34e7edd1284366d
Tx public key: cf97528ee3d6ccbf045d93a5b0b465296ee628c5276e38ac4dbcb4ab2ed4b91a
Timestamp: 1686262563 Timestamp [UCT]: 2023-06-08 22:16:03 Age [y:d:h:m:s]: 02:153:09:41:37
Block: 778107 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 629408 RingCT/type: yes/0
Extra: 01cf97528ee3d6ccbf045d93a5b0b465296ee628c5276e38ac4dbcb4ab2ed4b91a02110000000175e3f0e9000000000000000000

1 output(s) for total of 1.621095736000 dcy

stealth address amount amount idx
00: e2f1bdb7f37369c215f1fd06b1e9fd5159cf63a90d87dc893ea3837014f934b4 1.621095736000 1227724 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": 778117, "vin": [ { "gen": { "height": 778107 } } ], "vout": [ { "amount": 1621095736, "target": { "key": "e2f1bdb7f37369c215f1fd06b1e9fd5159cf63a90d87dc893ea3837014f934b4" } } ], "extra": [ 1, 207, 151, 82, 142, 227, 214, 204, 191, 4, 93, 147, 165, 176, 180, 101, 41, 110, 230, 40, 197, 39, 110, 56, 172, 77, 188, 180, 171, 46, 212, 185, 26, 2, 17, 0, 0, 0, 1, 117, 227, 240, 233, 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