Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0d859b3c4a1f7e4cac3578c3eef2720a5e45f64eb6834dddff05de380641d61b

Tx prefix hash: 111fe16b5ba7fdf8f8fde7cd11d5cf6677fda6a385b4f804cacc1957d0d3c6a2
Tx public key: 8fd26a799dae1b83e563c0d6bc80951219f5e5db16e0e2227f3b17a78007a47b
Timestamp: 1728713887 Timestamp [UCT]: 2024-10-12 06:18:07 Age [y:d:h:m:s]: 01:030:13:39:13
Block: 1129794 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 280225 RingCT/type: yes/0
Extra: 018fd26a799dae1b83e563c0d6bc80951219f5e5db16e0e2227f3b17a78007a47b021100000002e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9b9c5c28d2d0e2c823813142ea40989356adc76056c45820c854bdf5e80fb8de 0.600000000000 1612653 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": 1129804, "vin": [ { "gen": { "height": 1129794 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9b9c5c28d2d0e2c823813142ea40989356adc76056c45820c854bdf5e80fb8de" } } ], "extra": [ 1, 143, 210, 106, 121, 157, 174, 27, 131, 229, 99, 192, 214, 188, 128, 149, 18, 25, 245, 229, 219, 22, 224, 226, 34, 127, 59, 23, 167, 128, 7, 164, 123, 2, 17, 0, 0, 0, 2, 233, 20, 221, 21, 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