Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8cd9d822d0d73424fb8e2f4bfaf6a0e06f9c95f800158eb7935edaa25d0b5e01

Tx prefix hash: 42eeb1388c1c70c9f182ef59eb1159b31149ac24c05e1c804117243aa4d72bf9
Tx public key: 750410191a09fd36d42929fe5b1ad32e1addf0b7011d2fef610415e75ea26016
Timestamp: 1731224014 Timestamp [UCT]: 2024-11-10 07:33:34 Age [y:d:h:m:s]: 00:133:12:27:47
Block: 1150507 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 95257 RingCT/type: yes/0
Extra: 01750410191a09fd36d42929fe5b1ad32e1addf0b7011d2fef610415e75ea26016021100000004007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5848aa182a156434b25bf95173c96228b0dc31bf536d8db18c359f2c4d18c8f1 0.600000000000 1635846 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": 1150517, "vin": [ { "gen": { "height": 1150507 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5848aa182a156434b25bf95173c96228b0dc31bf536d8db18c359f2c4d18c8f1" } } ], "extra": [ 1, 117, 4, 16, 25, 26, 9, 253, 54, 212, 41, 41, 254, 91, 26, 211, 46, 26, 221, 240, 183, 1, 29, 47, 239, 97, 4, 21, 231, 94, 162, 96, 22, 2, 17, 0, 0, 0, 4, 0, 127, 151, 138, 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