Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 10caba840f5a7e8c4e14d29eb29396cdbf27163b155d6f41d0cd36d809737a4d

Tx prefix hash: a12aee320b9b1a50ca5a7e5edee5b2fed8070b595217a495ac9753ae9b3db53d
Tx public key: 01080fdc09d9b6f022b0e74e4febcc2cf3343a0fd8071a7a77b96e567973a945
Timestamp: 1669500774 Timestamp [UCT]: 2022-11-26 22:12:54 Age [y:d:h:m:s]: 02:168:07:40:53
Block: 639790 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 642033 RingCT/type: yes/0
Extra: 0101080fdc09d9b6f022b0e74e4febcc2cf3343a0fd8071a7a77b96e567973a94502110000000274b6d784000000000000000000

1 output(s) for total of 4.657041864000 dcy

stealth address amount amount idx
00: f61263589d463a6ec7bf594a7538c1e36ef7ef6669d2ae7fdf5da7d74592714d 4.657041864000 1079465 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": 639800, "vin": [ { "gen": { "height": 639790 } } ], "vout": [ { "amount": 4657041864, "target": { "key": "f61263589d463a6ec7bf594a7538c1e36ef7ef6669d2ae7fdf5da7d74592714d" } } ], "extra": [ 1, 1, 8, 15, 220, 9, 217, 182, 240, 34, 176, 231, 78, 79, 235, 204, 44, 243, 52, 58, 15, 216, 7, 26, 122, 119, 185, 110, 86, 121, 115, 169, 69, 2, 17, 0, 0, 0, 2, 116, 182, 215, 132, 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