Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: da6cbb91742a2d60b2d03dbf5a8c2379cd82d63da0e2b6fd1fccb170bd5d22bf

Tx prefix hash: a89282a6a0242a4e12532a7254d7e99705c8c37010e224593f5e7d666a118996
Tx public key: 1f0a65bbfb47d7f60de5296c19f2a8d468e243719926630d01fa3377269fb69d
Timestamp: 1722450196 Timestamp [UCT]: 2024-07-31 18:23:16 Age [y:d:h:m:s]: 01:102:01:42:24
Block: 1077861 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 331444 RingCT/type: yes/0
Extra: 011f0a65bbfb47d7f60de5296c19f2a8d468e243719926630d01fa3377269fb69d021100000007e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 83afd87ba45631b3cacb0a8764b2c3740e4563ee6faa951556e7e32bf34cdcd7 0.600000000000 1550416 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": 1077871, "vin": [ { "gen": { "height": 1077861 } } ], "vout": [ { "amount": 600000000, "target": { "key": "83afd87ba45631b3cacb0a8764b2c3740e4563ee6faa951556e7e32bf34cdcd7" } } ], "extra": [ 1, 31, 10, 101, 187, 251, 71, 215, 246, 13, 229, 41, 108, 25, 242, 168, 212, 104, 226, 67, 113, 153, 38, 99, 13, 1, 250, 51, 119, 38, 159, 182, 157, 2, 17, 0, 0, 0, 7, 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