Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bd0818a4a82c7a7b475ca089175b41e70bbeefddc24cd43df874bebb7b6df221

Tx prefix hash: 86db16e7651f660f427cb98258d3744da4eb02dd2695267a3134da0baaaf59b6
Tx public key: b0e4d1a37608cd6d7478dc956ce8bdf47f5405bd2c35d15f5522328886a8da03
Timestamp: 1706862969 Timestamp [UCT]: 2024-02-02 08:36:09 Age [y:d:h:m:s]: 01:280:07:10:30
Block: 948633 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 459110 RingCT/type: yes/0
Extra: 01b0e4d1a37608cd6d7478dc956ce8bdf47f5405bd2c35d15f5522328886a8da030211000000010011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 228e211ab32f27fdcc8924ac3cc7fe8c986ff42235b79c9066cfd7c2054b84b9 0.600000000000 1407081 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": 948643, "vin": [ { "gen": { "height": 948633 } } ], "vout": [ { "amount": 600000000, "target": { "key": "228e211ab32f27fdcc8924ac3cc7fe8c986ff42235b79c9066cfd7c2054b84b9" } } ], "extra": [ 1, 176, 228, 209, 163, 118, 8, 205, 109, 116, 120, 220, 149, 108, 232, 189, 244, 127, 84, 5, 189, 44, 53, 209, 95, 85, 34, 50, 136, 134, 168, 218, 3, 2, 17, 0, 0, 0, 1, 0, 17, 5, 91, 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