Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0932b6b1973199882a18412f8b6b6aeacc9265e40b859ab475968efa30a5d8f9

Tx prefix hash: a90f6112faf829e1b296600bc02550adcf15ea5a02d2b8ad983937a0110cbb3e
Tx public key: 4754579fff3c1be9620b9d2a536008be57d6c69efa620ef11192f951a9cfae2a
Timestamp: 1706309706 Timestamp [UCT]: 2024-01-26 22:55:06 Age [y:d:h:m:s]: 01:299:05:09:58
Block: 944026 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 472667 RingCT/type: yes/0
Extra: 014754579fff3c1be9620b9d2a536008be57d6c69efa620ef11192f951a9cfae2a0211000000040011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5fd8b07523ee699f0a67e23e26289160ad4cb829ee5056894831c2d74ecf07e6 0.600000000000 1402252 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": 944036, "vin": [ { "gen": { "height": 944026 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5fd8b07523ee699f0a67e23e26289160ad4cb829ee5056894831c2d74ecf07e6" } } ], "extra": [ 1, 71, 84, 87, 159, 255, 60, 27, 233, 98, 11, 157, 42, 83, 96, 8, 190, 87, 214, 198, 158, 250, 98, 14, 241, 17, 146, 249, 81, 169, 207, 174, 42, 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