Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5e3a997de1558035a3125f068c002c8270daf08acb0f54cbb8830741e9f1fd4c

Tx prefix hash: f4aaa277e7fba26ab4c9af3298b07b1052a481674286fdbeb414102935cc8453
Tx public key: 53350f5649058f402b7ff0d3955a0b6a9afea069e603ea7b940ef428255342c8
Timestamp: 1717789763 Timestamp [UCT]: 2024-06-07 19:49:23 Age [y:d:h:m:s]: 01:010:09:11:53
Block: 1039233 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 268187 RingCT/type: yes/0
Extra: 0153350f5649058f402b7ff0d3955a0b6a9afea069e603ea7b940ef428255342c802110000000e59dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: efe4d9528a47c737a517654afd5c9c0dd90c76842b8cdad12f07d930fa10104b 0.600000000000 1507862 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": 1039243, "vin": [ { "gen": { "height": 1039233 } } ], "vout": [ { "amount": 600000000, "target": { "key": "efe4d9528a47c737a517654afd5c9c0dd90c76842b8cdad12f07d930fa10104b" } } ], "extra": [ 1, 83, 53, 15, 86, 73, 5, 143, 64, 43, 127, 240, 211, 149, 90, 11, 106, 154, 254, 160, 105, 230, 3, 234, 123, 148, 14, 244, 40, 37, 83, 66, 200, 2, 17, 0, 0, 0, 14, 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