Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 969bc9cca558bc53ffdf002194a1efb52b863cde77562ed51a68b221dd310749

Tx prefix hash: 68a19d86eadcc618ae3b9fb13a75da92bba61384c36963247d0a2496e8b6b411
Tx public key: 5731f8b84b1ada06864d0a7f6cc9a82e252b68c9c50926e24565ec4e6af7381a
Timestamp: 1756412569 Timestamp [UCT]: 2025-08-28 20:22:49 Age [y:d:h:m:s]: 00:076:17:20:28
Block: 1356512 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 54751 RingCT/type: yes/0
Extra: 015731f8b84b1ada06864d0a7f6cc9a82e252b68c9c50926e24565ec4e6af7381a0211000000012609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a10ad8ae5f8d1d4702ed81091173f051fd152ccdd4ef74a7a16fbe81fa8bd3a8 0.600000000000 1844521 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": 1356522, "vin": [ { "gen": { "height": 1356512 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a10ad8ae5f8d1d4702ed81091173f051fd152ccdd4ef74a7a16fbe81fa8bd3a8" } } ], "extra": [ 1, 87, 49, 248, 184, 75, 26, 218, 6, 134, 77, 10, 127, 108, 201, 168, 46, 37, 43, 104, 201, 197, 9, 38, 226, 69, 101, 236, 78, 106, 247, 56, 26, 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