Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b2e0f3520d1064bef88d9b63cc89c2cdc28e4a22f8d05b611e7b1b014747701f

Tx prefix hash: ccc8603e20a0cd4ffecdf4501476578bf9053a088dc6cf8e727483250e102815
Tx public key: 060bf195cebf161a2ef2dfebe43659916177abd7392e1d4f1ff761392ad0b7c9
Timestamp: 1639160840 Timestamp [UCT]: 2021-12-10 18:27:20 Age [y:d:h:m:s]: 03:094:21:09:57
Block: 392670 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 846547 RingCT/type: yes/0
Extra: 01060bf195cebf161a2ef2dfebe43659916177abd7392e1d4f1ff761392ad0b7c90211000000161cab2639000000000000000000

1 output(s) for total of 30.685213431000 dcy

stealth address amount amount idx
00: 668736236e9ceb676640d22f7ce95aa3d358cbd3883289f4e18ebea2310a3e0e 30.685213431000 789625 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": 392680, "vin": [ { "gen": { "height": 392670 } } ], "vout": [ { "amount": 30685213431, "target": { "key": "668736236e9ceb676640d22f7ce95aa3d358cbd3883289f4e18ebea2310a3e0e" } } ], "extra": [ 1, 6, 11, 241, 149, 206, 191, 22, 26, 46, 242, 223, 235, 228, 54, 89, 145, 97, 119, 171, 215, 57, 46, 29, 79, 31, 247, 97, 57, 42, 208, 183, 201, 2, 17, 0, 0, 0, 22, 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