Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a1294fce8567580bd431c0a42540d86c49caf1c3112b0035cd1f0962852c7a7a

Tx prefix hash: bf92b0700c639f6f8fa60e7a539d3883e1038b1ce9268ddd6b323103ca362c8b
Tx public key: 2babe7dfb609e8b710d57a65ba00b6fc7f8e4d3b24d1cb316d1fe71d34d8ba17
Timestamp: 1753209221 Timestamp [UCT]: 2025-07-22 18:33:41 Age [y:d:h:m:s]: 00:128:15:32:21
Block: 1331128 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 90769 RingCT/type: yes/0
Extra: 012babe7dfb609e8b710d57a65ba00b6fc7f8e4d3b24d1cb316d1fe71d34d8ba1702110000000125a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e49f43d319a7d175ce685324b483e3efba498f915f800045f9fe978a34fb646c 0.600000000000 1818921 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": 1331138, "vin": [ { "gen": { "height": 1331128 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e49f43d319a7d175ce685324b483e3efba498f915f800045f9fe978a34fb646c" } } ], "extra": [ 1, 43, 171, 231, 223, 182, 9, 232, 183, 16, 213, 122, 101, 186, 0, 182, 252, 127, 142, 77, 59, 36, 209, 203, 49, 109, 31, 231, 29, 52, 216, 186, 23, 2, 17, 0, 0, 0, 1, 37, 163, 90, 15, 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