Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 899dd88d4dbbed1c319c56f72bf0f900f4af747156e21f08a97126e6160468e4

Tx prefix hash: f40cd88cb2faae77d389ea91944cbf78cc3d9e0549135ed467b2c54d48f6416a
Tx public key: 607ff7b594c06d5dc8e05eac91222bb71f7b5f37c0ea62d6415dcec37b6ca0e0
Timestamp: 1763166968 Timestamp [UCT]: 2025-11-15 00:36:08 Age [y:d:h:m:s]: 00:054:19:15:01
Block: 1412307 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 39248 RingCT/type: yes/0
Extra: 01607ff7b594c06d5dc8e05eac91222bb71f7b5f37c0ea62d6415dcec37b6ca0e002110000000425a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f9739c1dc3fcbc1537105b713bcb3bf1a5972fbc37585591f05e2dd80a25470f 0.600000000000 1900774 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": 1412317, "vin": [ { "gen": { "height": 1412307 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f9739c1dc3fcbc1537105b713bcb3bf1a5972fbc37585591f05e2dd80a25470f" } } ], "extra": [ 1, 96, 127, 247, 181, 148, 192, 109, 93, 200, 224, 94, 172, 145, 34, 43, 183, 31, 123, 95, 55, 192, 234, 98, 214, 65, 93, 206, 195, 123, 108, 160, 224, 2, 17, 0, 0, 0, 4, 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