Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4a49e968eb049fabf6f92e69515bd3d44787b7a70bc31e9803d8225f4a26f2bd

Tx prefix hash: 18ed1722a87ba201e48335ba6ae7a1ab9e2dd75c58362b06ff4df3d99061b46e
Tx public key: 1d845644a28d040eafeefc10c8331908c5db08c8611ae5edf338599d7b82027a
Timestamp: 1750678630 Timestamp [UCT]: 2025-06-23 11:37:10 Age [y:d:h:m:s]: 00:196:10:31:55
Block: 1311106 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 138377 RingCT/type: yes/0
Extra: 011d845644a28d040eafeefc10c8331908c5db08c8611ae5edf338599d7b82027a021100000005bf51b2a2000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c1bfc2e07216f58f831d9ed9a416433a748920de05e16a26cedde36664b8c605 0.600000000000 1798731 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": 1311116, "vin": [ { "gen": { "height": 1311106 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c1bfc2e07216f58f831d9ed9a416433a748920de05e16a26cedde36664b8c605" } } ], "extra": [ 1, 29, 132, 86, 68, 162, 141, 4, 14, 175, 238, 252, 16, 200, 51, 25, 8, 197, 219, 8, 200, 97, 26, 229, 237, 243, 56, 89, 157, 123, 130, 2, 122, 2, 17, 0, 0, 0, 5, 191, 81, 178, 162, 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