Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 522464b5f5caeffc086ec2dfb079b02770709d6a626435745fe4f2224930be9a

Tx prefix hash: 6b78974fa8af525974496da1b0968e17bcc14568927d76db531cab8effb5709e
Tx public key: dea8e0c7c2005ce6c40f0fb519129fe21f25e9ed2da94057ede7fd2c223bf8e8
Timestamp: 1715811320 Timestamp [UCT]: 2024-05-15 22:15:20 Age [y:d:h:m:s]: 00:285:09:15:22
Block: 1022833 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 203945 RingCT/type: yes/0
Extra: 01dea8e0c7c2005ce6c40f0fb519129fe21f25e9ed2da94057ede7fd2c223bf8e80211000000020011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 057ef81f7eab2aa5e275b3e6424aa958bf2d334c3e142b9439fe19f4f38cc235 0.600000000000 1487546 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": 1022843, "vin": [ { "gen": { "height": 1022833 } } ], "vout": [ { "amount": 600000000, "target": { "key": "057ef81f7eab2aa5e275b3e6424aa958bf2d334c3e142b9439fe19f4f38cc235" } } ], "extra": [ 1, 222, 168, 224, 199, 194, 0, 92, 230, 196, 15, 15, 181, 25, 18, 159, 226, 31, 37, 233, 237, 45, 169, 64, 87, 237, 231, 253, 44, 34, 59, 248, 232, 2, 17, 0, 0, 0, 2, 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