Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9a6f5dbd421cd7ddb9d4858f4bb3253aef92c227597244f303169560357146a9

Tx prefix hash: 490791f8486faacdfe3958554efa82e759764b0e787f64b42848a219c3ece74b
Tx public key: 4b1e9f1d8a145e6b93713b668df9ab68f343edf71ca9f227b1c5efda6923efe5
Timestamp: 1750946038 Timestamp [UCT]: 2025-06-26 13:53:58 Age [y:d:h:m:s]: 00:144:19:23:41
Block: 1313225 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 101489 RingCT/type: yes/0
Extra: 014b1e9f1d8a145e6b93713b668df9ab68f343edf71ca9f227b1c5efda6923efe5021100000001a11dba98000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bde91f70fd6ab75d59ad16cde1aeab6b6112abccac0e9ce3316ba17b670a5182 0.600000000000 1800864 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": 1313235, "vin": [ { "gen": { "height": 1313225 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bde91f70fd6ab75d59ad16cde1aeab6b6112abccac0e9ce3316ba17b670a5182" } } ], "extra": [ 1, 75, 30, 159, 29, 138, 20, 94, 107, 147, 113, 59, 102, 141, 249, 171, 104, 243, 67, 237, 247, 28, 169, 242, 39, 177, 197, 239, 218, 105, 35, 239, 229, 2, 17, 0, 0, 0, 1, 161, 29, 186, 152, 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