Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2105e0e69d142fd909cac5a8d873a9af7343dd344f40f3275e142a82368b2dd9

Tx prefix hash: bd4079e77df77162d701eb5bc44c3b1bc74357250505dc382403161a6f1cc021
Tx public key: 3aaf5de343e52ec8497bf3466a15a2e61bdb43e29c2a035eda25eef0e541ff68
Timestamp: 1704227237 Timestamp [UCT]: 2024-01-02 20:27:17 Age [y:d:h:m:s]: 01:077:01:38:34
Block: 926791 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 316204 RingCT/type: yes/0
Extra: 013aaf5de343e52ec8497bf3466a15a2e61bdb43e29c2a035eda25eef0e541ff680211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b27ef2bdd37ae8166c2ff31e052e16e530a44765e818781024d956c32131acc4 0.600000000000 1384589 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": 926801, "vin": [ { "gen": { "height": 926791 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b27ef2bdd37ae8166c2ff31e052e16e530a44765e818781024d956c32131acc4" } } ], "extra": [ 1, 58, 175, 93, 227, 67, 229, 46, 200, 73, 123, 243, 70, 106, 21, 162, 230, 27, 219, 67, 226, 156, 42, 3, 94, 218, 37, 238, 240, 229, 65, 255, 104, 2, 17, 0, 0, 0, 2, 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