Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ee98c76d4dfaaa36d40dae80c6c1d3d08451a687ac23c5613c6a9e98a0a9a326

Tx prefix hash: f67b934c043f89798378f8fc9960074c6b4bc54c6473ceb72467d21e76426ebe
Tx public key: b3f218fe96d43d36a50f7eb6d8b0a38df0e973fdb3cf1825884266d738a82dac
Timestamp: 1746922933 Timestamp [UCT]: 2025-05-11 00:22:13 Age [y:d:h:m:s]: 00:265:03:50:57
Block: 1280226 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 187141 RingCT/type: yes/0
Extra: 01b3f218fe96d43d36a50f7eb6d8b0a38df0e973fdb3cf1825884266d738a82dac0211000000039f9fe68c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6ff39495983b8df9cdc4eb76f636be5ba14bb057d880536eb0b972cf645de9ac 0.600000000000 1767609 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": 1280236, "vin": [ { "gen": { "height": 1280226 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6ff39495983b8df9cdc4eb76f636be5ba14bb057d880536eb0b972cf645de9ac" } } ], "extra": [ 1, 179, 242, 24, 254, 150, 212, 61, 54, 165, 15, 126, 182, 216, 176, 163, 141, 240, 233, 115, 253, 179, 207, 24, 37, 136, 66, 102, 215, 56, 168, 45, 172, 2, 17, 0, 0, 0, 3, 159, 159, 230, 140, 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