Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 77e6a720d4495dddc1c3c3c3da634ad98c4a95c8590faed1b0c62ca60aef756a

Tx prefix hash: 3633d93cd6dd299009651e4b5c494f90318f82ebc15034141e863025eb0188e8
Tx public key: a62e637fbae33bc3f26193482de53866bb2bdc02b7249f93e07322b48ec9ec81
Timestamp: 1703192921 Timestamp [UCT]: 2023-12-21 21:08:41 Age [y:d:h:m:s]: 01:106:19:55:50
Block: 918213 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 337466 RingCT/type: yes/0
Extra: 01a62e637fbae33bc3f26193482de53866bb2bdc02b7249f93e07322b48ec9ec8102110000000d7a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 77aa6564f4ec1ef4f19a621bf392a0da84cbfaed4e9d499fdc6dda5a90ea52ea 0.600000000000 1375855 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": 918223, "vin": [ { "gen": { "height": 918213 } } ], "vout": [ { "amount": 600000000, "target": { "key": "77aa6564f4ec1ef4f19a621bf392a0da84cbfaed4e9d499fdc6dda5a90ea52ea" } } ], "extra": [ 1, 166, 46, 99, 127, 186, 227, 59, 195, 242, 97, 147, 72, 45, 229, 56, 102, 187, 43, 220, 2, 183, 36, 159, 147, 224, 115, 34, 180, 142, 201, 236, 129, 2, 17, 0, 0, 0, 13, 122, 156, 244, 199, 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