Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a03d1b772f55193f2072e55d26e0a42d2b3643dfaad4ebf43d2c0087ab952347

Tx prefix hash: 157975ee6e24b91839a79b6e5ca53b4a4a62682e478c28de3ebdff091f50592f
Tx public key: 3231c3f91a630bcd644950bd8616744bb37694a5d6acbeebda0d4a69cb847a7e
Timestamp: 1730832775 Timestamp [UCT]: 2024-11-05 18:52:55 Age [y:d:h:m:s]: 00:018:12:41:11
Block: 1147272 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 13269 RingCT/type: yes/0
Extra: 013231c3f91a630bcd644950bd8616744bb37694a5d6acbeebda0d4a69cb847a7e021100000004007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9d571fc9e409d5d3e53b166f025434339721bcdf01c85e3f791a54eb3366adc2 0.600000000000 1631967 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": 1147282, "vin": [ { "gen": { "height": 1147272 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9d571fc9e409d5d3e53b166f025434339721bcdf01c85e3f791a54eb3366adc2" } } ], "extra": [ 1, 50, 49, 195, 249, 26, 99, 11, 205, 100, 73, 80, 189, 134, 22, 116, 75, 179, 118, 148, 165, 214, 172, 190, 235, 218, 13, 74, 105, 203, 132, 122, 126, 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