Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bdcfc5d3c4d8c12f793d7254e63ed25132eb06035123ea2f2a12eb29f2030f0c

Tx prefix hash: cab56004f39c32e9586033f28915f5ac75eb0ad3b907abf5bae5cca61b1f1ecf
Tx public key: 8d5fad27b5557eecc1746d5c941eeb20ca1bdbc00de3b704da1fb82091db51e6
Timestamp: 1708238619 Timestamp [UCT]: 2024-02-18 06:43:39 Age [y:d:h:m:s]: 01:007:10:11:22
Block: 960044 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 266306 RingCT/type: yes/0
Extra: 018d5fad27b5557eecc1746d5c941eeb20ca1bdbc00de3b704da1fb82091db51e60211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: db3fbdcbe506fbce1e4d70e919e706f2759f7e7e9f4efbc4b7d1055da8ec5c1e 0.600000000000 1419603 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": 960054, "vin": [ { "gen": { "height": 960044 } } ], "vout": [ { "amount": 600000000, "target": { "key": "db3fbdcbe506fbce1e4d70e919e706f2759f7e7e9f4efbc4b7d1055da8ec5c1e" } } ], "extra": [ 1, 141, 95, 173, 39, 181, 85, 126, 236, 193, 116, 109, 92, 148, 30, 235, 32, 202, 27, 219, 192, 13, 227, 183, 4, 218, 31, 184, 32, 145, 219, 81, 230, 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