Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a7ab849296d73ac2d54300a29ca54047eb6a8e0cfd1b9ba3c14b6a2a2c9e3abc

Tx prefix hash: f5f3991035c399b9c1f926c4256f641bab976f4022c20442da4b1f6b9d64c4e6
Tx public key: c715169268a4ae04f8eb125c80c7a381576241b8d60ae072a73b46cb1f2aeb3e
Timestamp: 1737678272 Timestamp [UCT]: 2025-01-24 00:24:32 Age [y:d:h:m:s]: 00:332:03:28:03
Block: 1203920 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 234973 RingCT/type: yes/0
Extra: 01c715169268a4ae04f8eb125c80c7a381576241b8d60ae072a73b46cb1f2aeb3e02110000000a007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 478f75257a33829a30637574630809843fd56ea768eff785a204ce8e319d0792 0.600000000000 1690601 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": 1203930, "vin": [ { "gen": { "height": 1203920 } } ], "vout": [ { "amount": 600000000, "target": { "key": "478f75257a33829a30637574630809843fd56ea768eff785a204ce8e319d0792" } } ], "extra": [ 1, 199, 21, 22, 146, 104, 164, 174, 4, 248, 235, 18, 92, 128, 199, 163, 129, 87, 98, 65, 184, 214, 10, 224, 114, 167, 59, 70, 203, 31, 42, 235, 62, 2, 17, 0, 0, 0, 10, 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