Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 85844928eb5937130dfb6f5711ca7ea29725db6e2840563876d2b6fbbb686809

Tx prefix hash: 38c19b82f9470214375a774e921da911c133ca916e85ce42c1f72fbc6e7e201e
Tx public key: d298fb8a4a9ccf5287c11362926c0d4e8106df7a4c6651c358053cef67a948ef
Timestamp: 1716001180 Timestamp [UCT]: 2024-05-18 02:59:40 Age [y:d:h:m:s]: 00:364:18:14:43
Block: 1024395 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 260740 RingCT/type: yes/0
Extra: 01d298fb8a4a9ccf5287c11362926c0d4e8106df7a4c6651c358053cef67a948ef02110000000459dad3f5000000000000000000

1 output(s) for total of 0.615610000000 dcy

stealth address amount amount idx
00: 6054bc0a1c9f21cfc05949507ca9c94845378efa91dc0208075e25ac79be0d37 0.615610000000 1490112 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": 1024405, "vin": [ { "gen": { "height": 1024395 } } ], "vout": [ { "amount": 615610000, "target": { "key": "6054bc0a1c9f21cfc05949507ca9c94845378efa91dc0208075e25ac79be0d37" } } ], "extra": [ 1, 210, 152, 251, 138, 74, 156, 207, 82, 135, 193, 19, 98, 146, 108, 13, 78, 129, 6, 223, 122, 76, 102, 81, 195, 88, 5, 60, 239, 103, 169, 72, 239, 2, 17, 0, 0, 0, 4, 89, 218, 211, 245, 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