Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a5f2ab765a3e4c5cc55b934bf0834f1f789bcb65dd350d1258b7b2337949adb6

Tx prefix hash: 53abd09cd5d8e9d22175f9d217e51c0946aa3b45b2de26f4fea8a073ce787cd6
Tx public key: 0b204ea061578bd14fba22e35efdd87a800ccd702f272e6c057adeb72e849060
Timestamp: 1577707296 Timestamp [UCT]: 2019-12-30 12:01:36 Age [y:d:h:m:s]: 05:306:14:49:02
Block: 35000 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1366641 RingCT/type: yes/0
Extra: 010b204ea061578bd14fba22e35efdd87a800ccd702f272e6c057adeb72e8490600211000000034943cd9f000000000000000000

1 output(s) for total of 469.928003406000 dcy

stealth address amount amount idx
00: 67ca9b580ddf98a195eaf8c24ad90bc0d7e6c917c8e5a85824188be8b9f45bae 469.928003406000 58967 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": 35010, "vin": [ { "gen": { "height": 35000 } } ], "vout": [ { "amount": 469928003406, "target": { "key": "67ca9b580ddf98a195eaf8c24ad90bc0d7e6c917c8e5a85824188be8b9f45bae" } } ], "extra": [ 1, 11, 32, 78, 160, 97, 87, 139, 209, 79, 186, 34, 227, 94, 253, 216, 122, 128, 12, 205, 112, 47, 39, 46, 108, 5, 122, 222, 183, 46, 132, 144, 96, 2, 17, 0, 0, 0, 3, 73, 67, 205, 159, 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