Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 66936d3e9522c8c33ad912d9ccf25f8d16162d0982f4a41e036ffb38aee8b0a2

Tx prefix hash: 60301ca6d6d0c5cf505c54af775f1c89610e05f627779089e8613bc9c0526a96
Tx public key: ec9b768c905d56d7374d19a7e1fe6a7cdd684d488a71e481f071555b0b667640
Timestamp: 1725265290 Timestamp [UCT]: 2024-09-02 08:21:30 Age [y:d:h:m:s]: 00:215:22:44:37
Block: 1101205 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 154184 RingCT/type: yes/0
Extra: 01ec9b768c905d56d7374d19a7e1fe6a7cdd684d488a71e481f071555b0b66764002110000000591e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2a08e7087dc055a07504cb495d449cd914ff6327a2acc13be69676ab732275f0 0.600000000000 1577190 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": 1101215, "vin": [ { "gen": { "height": 1101205 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2a08e7087dc055a07504cb495d449cd914ff6327a2acc13be69676ab732275f0" } } ], "extra": [ 1, 236, 155, 118, 140, 144, 93, 86, 215, 55, 77, 25, 167, 225, 254, 106, 124, 221, 104, 77, 72, 138, 113, 228, 129, 240, 113, 85, 91, 11, 102, 118, 64, 2, 17, 0, 0, 0, 5, 145, 225, 60, 4, 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