Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 523d0e1feb44014a4ccedab18597576f4e47a3523c0e22d32da3cd972be8ac64

Tx prefix hash: 134ab5c83dab6a72fc88aaf8682e1cf9156b57dda15472e0f037c043fefd130b
Tx public key: b4c98b7aa588238ee4055ae48abdf36fe4b8c4c702378943f246e23a53829a5e
Timestamp: 1751376831 Timestamp [UCT]: 2025-07-01 13:33:51 Age [y:d:h:m:s]: 00:139:01:10:47
Block: 1316562 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 97596 RingCT/type: yes/0
Extra: 01b4c98b7aa588238ee4055ae48abdf36fe4b8c4c702378943f246e23a53829a5e021100000003dfc3ba49000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2ce6a1ad290637bd558eb6bb7cb9c9eb28c37a3c4f884071d0b91eeade13146d 0.600000000000 1804223 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": 1316572, "vin": [ { "gen": { "height": 1316562 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2ce6a1ad290637bd558eb6bb7cb9c9eb28c37a3c4f884071d0b91eeade13146d" } } ], "extra": [ 1, 180, 201, 139, 122, 165, 136, 35, 142, 228, 5, 90, 228, 138, 189, 243, 111, 228, 184, 196, 199, 2, 55, 137, 67, 242, 70, 226, 58, 83, 130, 154, 94, 2, 17, 0, 0, 0, 3, 223, 195, 186, 73, 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