Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b6f724c162071ac87ba4f7fdf6fa03d6ae8563222a9159aa8613653722b76a1d

Tx prefix hash: cef6d7e4b0b0f0bb8b03953633c5f12dd69b1ef5400902a7f99b76e0cb56e384
Tx public key: 454fe93c962eccce0fc30e4717a19bc1ffb91ea0f92925875036460f899b9ec0
Timestamp: 1635245172 Timestamp [UCT]: 2021-10-26 10:46:12 Age [y:d:h:m:s]: 03:062:11:04:08
Block: 360853 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 823004 RingCT/type: yes/0
Extra: 01454fe93c962eccce0fc30e4717a19bc1ffb91ea0f92925875036460f899b9ec00211000000144f792ffd000000000000000000

1 output(s) for total of 39.115115906000 dcy

stealth address amount amount idx
00: 6015effa5a2dde68fb8b7bc50e1b696e7361edcd81ecf5aaea5f361e5051944b 39.115115906000 734334 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": 360863, "vin": [ { "gen": { "height": 360853 } } ], "vout": [ { "amount": 39115115906, "target": { "key": "6015effa5a2dde68fb8b7bc50e1b696e7361edcd81ecf5aaea5f361e5051944b" } } ], "extra": [ 1, 69, 79, 233, 60, 150, 46, 204, 206, 15, 195, 14, 71, 23, 161, 155, 193, 255, 185, 30, 160, 249, 41, 37, 135, 80, 54, 70, 15, 137, 155, 158, 192, 2, 17, 0, 0, 0, 20, 79, 121, 47, 253, 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