Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 94d5d3e8bd639119d4a4251cc78762ebff5a90ae741ca70e9d1785a3d0e8aae6

Tx prefix hash: f93b851989e2d824709164defd93f467bd4a22e2b9cc1920615872eee965e480
Tx public key: 322236c9c969760dc6b5e31f8c210134edc78d6a1fe75aa8c468ef1d83e271d3
Timestamp: 1712858569 Timestamp [UCT]: 2024-04-11 18:02:49 Age [y:d:h:m:s]: 01:042:02:24:22
Block: 998322 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 291098 RingCT/type: yes/0
Extra: 01322236c9c969760dc6b5e31f8c210134edc78d6a1fe75aa8c468ef1d83e271d30211000000050011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a5fc7bc9827f578f61cd71aba0e2dcc03e52ffff93855a1338c926adcda271aa 0.600000000000 1458768 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": 998332, "vin": [ { "gen": { "height": 998322 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a5fc7bc9827f578f61cd71aba0e2dcc03e52ffff93855a1338c926adcda271aa" } } ], "extra": [ 1, 50, 34, 54, 201, 201, 105, 118, 13, 198, 181, 227, 31, 140, 33, 1, 52, 237, 199, 141, 106, 31, 231, 90, 168, 196, 104, 239, 29, 131, 226, 113, 211, 2, 17, 0, 0, 0, 5, 0, 17, 5, 91, 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