Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e744fa23e6bb6d863580db3ae5e564f56b174a6d0824ba6572d9cfea80ff846a

Tx prefix hash: 2e73339eb4cc4f11d89b23ec223f51b2d171e93cbb8fd20665db715f2998d825
Tx public key: adc10a4a6374ec1de641645b8afbc360974d4a46676399dc9b14a9027aa4d866
Timestamp: 1702506837 Timestamp [UCT]: 2023-12-13 22:33:57 Age [y:d:h:m:s]: 01:133:14:36:34
Block: 912524 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 356642 RingCT/type: yes/0
Extra: 01adc10a4a6374ec1de641645b8afbc360974d4a46676399dc9b14a9027aa4d86602110000000233af99f4000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b9d3a2415a566d5b9419df5a4a1785822abf1ef0b39ae73afd1e53fc19ac9e91 0.600000000000 1369752 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": 912534, "vin": [ { "gen": { "height": 912524 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b9d3a2415a566d5b9419df5a4a1785822abf1ef0b39ae73afd1e53fc19ac9e91" } } ], "extra": [ 1, 173, 193, 10, 74, 99, 116, 236, 29, 230, 65, 100, 91, 138, 251, 195, 96, 151, 77, 74, 70, 103, 99, 153, 220, 155, 20, 169, 2, 122, 164, 216, 102, 2, 17, 0, 0, 0, 2, 51, 175, 153, 244, 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