Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 361f9a226ebab57f6fe1f0b0072d79bcf7350465807b1d9f3f92a952ec29f6fc

Tx prefix hash: 2de71767d0e2ef396f63df7be6853f3b40160dc30421cfb3c0579cd6911bcdd4
Tx public key: 6df47b5b62b5ce75797ceeddcf46ef47447d416d8ff9f69b626f57949d057e59
Timestamp: 1752291874 Timestamp [UCT]: 2025-07-12 03:44:34 Age [y:d:h:m:s]: 00:132:00:20:11
Block: 1323649 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 93043 RingCT/type: yes/0
Extra: 016df47b5b62b5ce75797ceeddcf46ef47447d416d8ff9f69b626f57949d057e59021100000001dfc3ba49000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4e45aff915cc62579df681bbe80064b0141c40e5d4be3e2b2b0f650f8ae71c37 0.600000000000 1811388 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": 1323659, "vin": [ { "gen": { "height": 1323649 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4e45aff915cc62579df681bbe80064b0141c40e5d4be3e2b2b0f650f8ae71c37" } } ], "extra": [ 1, 109, 244, 123, 91, 98, 181, 206, 117, 121, 124, 238, 221, 207, 70, 239, 71, 68, 125, 65, 109, 143, 249, 246, 155, 98, 111, 87, 148, 157, 5, 126, 89, 2, 17, 0, 0, 0, 1, 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