Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f219753151e264569a57334d83093a3e8a484183562a07326556f5c2c1befdfc

Tx prefix hash: a6f09c0c410990672d00a7173321e0b403eee930d6c3c5ea788b8660f791da7a
Tx public key: 849e1766455628254f4358132041d356b65b4fae5b190e86d39c0d45f3d282ad
Timestamp: 1716971401 Timestamp [UCT]: 2024-05-29 08:30:01 Age [y:d:h:m:s]: 00:306:15:33:08
Block: 1032454 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 219160 RingCT/type: yes/0
Extra: 01849e1766455628254f4358132041d356b65b4fae5b190e86d39c0d45f3d282ad0211000000050011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: eb7632637e8605a03e7e08d48e5ad05a3b9ec9df31a573f2c92c473dc9cfb533 0.600000000000 1500907 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": 1032464, "vin": [ { "gen": { "height": 1032454 } } ], "vout": [ { "amount": 600000000, "target": { "key": "eb7632637e8605a03e7e08d48e5ad05a3b9ec9df31a573f2c92c473dc9cfb533" } } ], "extra": [ 1, 132, 158, 23, 102, 69, 86, 40, 37, 79, 67, 88, 19, 32, 65, 211, 86, 182, 91, 79, 174, 91, 25, 14, 134, 211, 156, 13, 69, 243, 210, 130, 173, 2, 17, 0, 0, 0, 5, 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