Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b49c3aff0c5e38b3f8e9af3e0cf2fcdb30ebdbb402f0939444272023b7bee4e9

Tx prefix hash: b9775140d3e0f9929e97f095719e3437cb494a317ce36b2996f835f271875b62
Tx public key: 8661cf533057d3c09d7570f2d82bea26ee3c915145836b944c78c8f6fc0893d5
Timestamp: 1720663237 Timestamp [UCT]: 2024-07-11 02:00:37 Age [y:d:h:m:s]: 01:090:06:47:42
Block: 1063064 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 322982 RingCT/type: yes/0
Extra: 018661cf533057d3c09d7570f2d82bea26ee3c915145836b944c78c8f6fc0893d5021100000003e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3372816a57e5bad24e94c71711c7375aaf806e9c6ce224e4f297adfac03f8e4a 0.600000000000 1533577 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": 1063074, "vin": [ { "gen": { "height": 1063064 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3372816a57e5bad24e94c71711c7375aaf806e9c6ce224e4f297adfac03f8e4a" } } ], "extra": [ 1, 134, 97, 207, 83, 48, 87, 211, 192, 157, 117, 112, 242, 216, 43, 234, 38, 238, 60, 145, 81, 69, 131, 107, 148, 76, 120, 200, 246, 252, 8, 147, 213, 2, 17, 0, 0, 0, 3, 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