Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dc5525fd6506fb05de253c0ad2a747894ba527719d190cb3be90f4cc61455a83

Tx prefix hash: d9f3579a059c6538774c9b6a4583701deb2e00ab4aa3ff739dbe363bfab2817d
Tx public key: f28a8b5fdd3f72c3b5d0806e9bf7b2de17c3f964427ebc05565b34fa96357e7d
Timestamp: 1756078040 Timestamp [UCT]: 2025-08-24 23:27:20 Age [y:d:h:m:s]: 00:093:15:38:05
Block: 1353741 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 66870 RingCT/type: yes/0
Extra: 01f28a8b5fdd3f72c3b5d0806e9bf7b2de17c3f964427ebc05565b34fa96357e7d0211000000032609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 65683a3313e90f46f0fbcb559a0a288b93db2a4deede60ce727447917e2743cc 0.600000000000 1841718 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": 1353751, "vin": [ { "gen": { "height": 1353741 } } ], "vout": [ { "amount": 600000000, "target": { "key": "65683a3313e90f46f0fbcb559a0a288b93db2a4deede60ce727447917e2743cc" } } ], "extra": [ 1, 242, 138, 139, 95, 221, 63, 114, 195, 181, 208, 128, 110, 155, 247, 178, 222, 23, 195, 249, 100, 66, 126, 188, 5, 86, 91, 52, 250, 150, 53, 126, 125, 2, 17, 0, 0, 0, 3, 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