Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f1304452bc1d74133ca958a8ddec4023f8b2c2e26303a76729aa2b34181b7682

Tx prefix hash: af9f7e128314e7151938c8b543137ba66e7c207db6892683d5b2c75b4778f00d
Tx public key: 4b1691f4b34adee1d9f9763f18fe804820fe0e599fba1b681db5ca628e60e15d
Timestamp: 1694984892 Timestamp [UCT]: 2023-09-17 21:08:12 Age [y:d:h:m:s]: 01:206:06:23:43
Block: 850353 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 408516 RingCT/type: yes/0
Extra: 014b1691f4b34adee1d9f9763f18fe804820fe0e599fba1b681db5ca628e60e15d02110000000133af99f4000000000000000000

1 output(s) for total of 0.934173555000 dcy

stealth address amount amount idx
00: 1949c19793ff19b03a96030a89537b854ec75d7ffda40d36a29ef73d0c367d36 0.934173555000 1304067 of 0

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": 850363, "vin": [ { "gen": { "height": 850353 } } ], "vout": [ { "amount": 934173555, "target": { "key": "1949c19793ff19b03a96030a89537b854ec75d7ffda40d36a29ef73d0c367d36" } } ], "extra": [ 1, 75, 22, 145, 244, 179, 74, 222, 225, 217, 249, 118, 63, 24, 254, 128, 72, 32, 254, 14, 89, 159, 186, 27, 104, 29, 181, 202, 98, 142, 96, 225, 93, 2, 17, 0, 0, 0, 1, 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