Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 424e38554b2628099c0b4d0404f2316e49d3ab92270f03dc5f4e2c1b02bc455a

Tx prefix hash: 512d12a77a64ac850d8262a22f380e5882a26b3d0df205e99e950adc24fc084a
Tx public key: f782dd5077e5cdcabcdfb7e49133f0adc158bf781ee87730dee22958b2e5c448
Timestamp: 1716077527 Timestamp [UCT]: 2024-05-19 00:12:07 Age [y:d:h:m:s]: 00:329:20:47:02
Block: 1025035 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 235782 RingCT/type: yes/0
Extra: 01f782dd5077e5cdcabcdfb7e49133f0adc158bf781ee87730dee22958b2e5c4480211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e2da59b4c095d19b5a83bd525d1a8b13f167bd21af551d06a72fbc6ee4d5d33b 0.600000000000 1491246 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": 1025045, "vin": [ { "gen": { "height": 1025035 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e2da59b4c095d19b5a83bd525d1a8b13f167bd21af551d06a72fbc6ee4d5d33b" } } ], "extra": [ 1, 247, 130, 221, 80, 119, 229, 205, 202, 188, 223, 183, 228, 145, 51, 240, 173, 193, 88, 191, 120, 30, 232, 119, 48, 222, 226, 41, 88, 178, 229, 196, 72, 2, 17, 0, 0, 0, 3, 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