Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d0fe23193b3eda9fb6086f59e25dc4cd64d4d875a49de700badc930d371c555d

Tx prefix hash: abf64c723fe85960b2a7e9e5c19c44a3d0f2a1cabb2ad78933379f25e75ef53f
Tx public key: cc9e9fcc6a215ea30f411222eb8fe4ad59e2e491c1f5a308d8277dc9f5db057a
Timestamp: 1638649891 Timestamp [UCT]: 2021-12-04 20:31:31 Age [y:d:h:m:s]: 03:099:23:34:29
Block: 388471 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 850164 RingCT/type: yes/0
Extra: 01cc9e9fcc6a215ea30f411222eb8fe4ad59e2e491c1f5a308d8277dc9f5db057a0211000000031cab2639000000000000000000

1 output(s) for total of 31.683611787000 dcy

stealth address amount amount idx
00: 2cdafa17d8bb0e67aae74da3745637cbca71f60f17504632d35a7de8d8acdb98 31.683611787000 783124 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": 388481, "vin": [ { "gen": { "height": 388471 } } ], "vout": [ { "amount": 31683611787, "target": { "key": "2cdafa17d8bb0e67aae74da3745637cbca71f60f17504632d35a7de8d8acdb98" } } ], "extra": [ 1, 204, 158, 159, 204, 106, 33, 94, 163, 15, 65, 18, 34, 235, 143, 228, 173, 89, 226, 228, 145, 193, 245, 163, 8, 216, 39, 125, 201, 245, 219, 5, 122, 2, 17, 0, 0, 0, 3, 28, 171, 38, 57, 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