Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e906c1a93a396c60274ef476edb33289dbb36d9ffdb1ee0fc20364908079b8b5

Tx prefix hash: ae2e87435c804732bb34c86c0a70c2c09bc6c3c8cf288d457b47af78fa72634f
Tx public key: 590497b25f428acd2202bdfcd1755ab29dcd24c840e2aa8ae337efed90d43d9d
Timestamp: 1722151475 Timestamp [UCT]: 2024-07-28 07:24:35 Age [y:d:h:m:s]: 00:164:21:59:47
Block: 1075389 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 118000 RingCT/type: yes/0
Extra: 01590497b25f428acd2202bdfcd1755ab29dcd24c840e2aa8ae337efed90d43d9d02110000000891e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 92d4cc8fa2b1db6f47498f55f089dc5a7d8d4249ff3c084be6bd9723bc208ab9 0.600000000000 1547914 of 15

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": 1075399, "vin": [ { "gen": { "height": 1075389 } } ], "vout": [ { "amount": 600000000, "target": { "key": "92d4cc8fa2b1db6f47498f55f089dc5a7d8d4249ff3c084be6bd9723bc208ab9" } } ], "extra": [ 1, 89, 4, 151, 178, 95, 66, 138, 205, 34, 2, 189, 252, 209, 117, 90, 178, 157, 205, 36, 200, 64, 226, 170, 138, 227, 55, 239, 237, 144, 212, 61, 157, 2, 17, 0, 0, 0, 8, 145, 225, 60, 4, 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