Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 874f7bb568d6a52b6450ff66a985ab01c613aa41bd9d3356bb851ada7c8de136

Tx prefix hash: 8f47284e03158dfc1e416a996e82c8544231fbf7211e60ce1cb57e5f5af72dfe
Tx public key: 564b6929dc61b409cde5396315b0f62e4816ab2a80c4700e8fb2d9516ad71f8f
Timestamp: 1762004142 Timestamp [UCT]: 2025-11-01 13:35:42 Age [y:d:h:m:s]: 00:007:16:04:42
Block: 1402695 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 5465 RingCT/type: yes/0
Extra: 01564b6929dc61b409cde5396315b0f62e4816ab2a80c4700e8fb2d9516ad71f8f021100000001df5a247a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a0d36c7bbe0d9a89c19842df979e226645f7903d5103e921a5a9d46c7f32676c 0.600000000000 1891014 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": 1402705, "vin": [ { "gen": { "height": 1402695 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a0d36c7bbe0d9a89c19842df979e226645f7903d5103e921a5a9d46c7f32676c" } } ], "extra": [ 1, 86, 75, 105, 41, 220, 97, 180, 9, 205, 229, 57, 99, 21, 176, 246, 46, 72, 22, 171, 42, 128, 196, 112, 14, 143, 178, 217, 81, 106, 215, 31, 143, 2, 17, 0, 0, 0, 1, 223, 90, 36, 122, 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