Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e6e968bc1fad62481af58806e5f126d0f84d70ede69efe42b9b21888ac624e72

Tx prefix hash: d4ffe64f02941eae6fa20afb6d0c7edb08af7af7d9931d96e03f7315f3cc6488
Tx public key: 1e343e86cf439050ecefc0c83d7b585208d7b946b36d3da4206f2a4d8ec41d4b
Timestamp: 1719308995 Timestamp [UCT]: 2024-06-25 09:49:55 Age [y:d:h:m:s]: 00:267:13:26:56
Block: 1051817 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 191213 RingCT/type: yes/0
Extra: 011e343e86cf439050ecefc0c83d7b585208d7b946b36d3da4206f2a4d8ec41d4b0211000000040011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 672796842a9201269c9aa5559a3a055dcae2c5c946cc932e24159bdb187c8444 0.600000000000 1522136 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": 1051827, "vin": [ { "gen": { "height": 1051817 } } ], "vout": [ { "amount": 600000000, "target": { "key": "672796842a9201269c9aa5559a3a055dcae2c5c946cc932e24159bdb187c8444" } } ], "extra": [ 1, 30, 52, 62, 134, 207, 67, 144, 80, 236, 239, 192, 200, 61, 123, 88, 82, 8, 215, 185, 70, 179, 109, 61, 164, 32, 111, 42, 77, 142, 196, 29, 75, 2, 17, 0, 0, 0, 4, 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