Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3558df480f50d907103515f11d8abf4949268946bf90022083ba0d6acec313b3

Tx prefix hash: 71c688788dc0eb401ab1a9c76a08c66323dccb6f7ef4cc835783beccfe515a36
Tx public key: 20abdbdd63bc8f62a8fd1199377fb5a4c6dbfdbbb2e2b051cab084a11f9f8c24
Timestamp: 1756115263 Timestamp [UCT]: 2025-08-25 09:47:43 Age [y:d:h:m:s]: 00:133:16:51:59
Block: 1354050 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 95545 RingCT/type: yes/0
Extra: 0120abdbdd63bc8f62a8fd1199377fb5a4c6dbfdbbb2e2b051cab084a11f9f8c240211000000012609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 959865bfd018d98a8c164758a99e332042022004f69eaa1065380bdb6a1c5748 0.600000000000 1842031 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": 1354060, "vin": [ { "gen": { "height": 1354050 } } ], "vout": [ { "amount": 600000000, "target": { "key": "959865bfd018d98a8c164758a99e332042022004f69eaa1065380bdb6a1c5748" } } ], "extra": [ 1, 32, 171, 219, 221, 99, 188, 143, 98, 168, 253, 17, 153, 55, 127, 181, 164, 198, 219, 253, 187, 178, 226, 176, 81, 202, 176, 132, 161, 31, 159, 140, 36, 2, 17, 0, 0, 0, 1, 38, 9, 179, 160, 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