Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 811a6a0f14ec537262adb926757645df9e99bb229dbe46695d0c63f761fb6402

Tx prefix hash: c0a8c9b8205a74522bed3d8a499cf68d11aa0110d973e893378e0665697e3cc0
Tx public key: f155d00354d7a3c71fb4f921be604a0d959306cfb6863119ea8e922ac5a0bfe4
Timestamp: 1745989653 Timestamp [UCT]: 2025-04-30 05:07:33 Age [y:d:h:m:s]: 00:013:12:30:45
Block: 1272511 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 9673 RingCT/type: yes/0
Extra: 01f155d00354d7a3c71fb4f921be604a0d959306cfb6863119ea8e922ac5a0bfe402110000000225a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1fb70f72dffae450d5ab70189ab89742b47e810006db51fde5c59c3482fe1d07 0.600000000000 1759786 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": 1272521, "vin": [ { "gen": { "height": 1272511 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1fb70f72dffae450d5ab70189ab89742b47e810006db51fde5c59c3482fe1d07" } } ], "extra": [ 1, 241, 85, 208, 3, 84, 215, 163, 199, 31, 180, 249, 33, 190, 96, 74, 13, 149, 147, 6, 207, 182, 134, 49, 25, 234, 142, 146, 42, 197, 160, 191, 228, 2, 17, 0, 0, 0, 2, 37, 163, 90, 15, 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