Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0077e222c398ebf1dc77b074a0ff95fe151106cf62671a7f03b8ddca0289943a

Tx prefix hash: 4b711b766a46587b0cb0641d020ebad7bbd3433851e91780181b961a16ce427a
Tx public key: a7c83e2eb3d61d9afb920e5811cc300b4ee113a4a5abb539b713f8ab9bfcd1ee
Timestamp: 1721991334 Timestamp [UCT]: 2024-07-26 10:55:34 Age [y:d:h:m:s]: 00:266:03:57:43
Block: 1074061 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 190154 RingCT/type: yes/0
Extra: 01a7c83e2eb3d61d9afb920e5811cc300b4ee113a4a5abb539b713f8ab9bfcd1ee021100000007e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 82e6baa85e2b3883c3a6b98e0155773ef8505bf19fcf9d6e9c2fdb083f733b66 0.600000000000 1546574 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": 1074071, "vin": [ { "gen": { "height": 1074061 } } ], "vout": [ { "amount": 600000000, "target": { "key": "82e6baa85e2b3883c3a6b98e0155773ef8505bf19fcf9d6e9c2fdb083f733b66" } } ], "extra": [ 1, 167, 200, 62, 46, 179, 214, 29, 154, 251, 146, 14, 88, 17, 204, 48, 11, 78, 225, 19, 164, 165, 171, 181, 57, 183, 19, 248, 171, 155, 252, 209, 238, 2, 17, 0, 0, 0, 7, 233, 20, 221, 21, 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