Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 55c22fc73f8d75b8d50ca0738541e70666a076924cb073a27ca3a326d1160de1

Tx prefix hash: 4f46900422791e24a131e2a62e22ce22268583991b5576b39e59d196526d2111
Tx public key: 77282f4433714486427d4964f7f1ef8a35b9213b0a1217eac09bcbe6df0de8f7
Timestamp: 1631438238 Timestamp [UCT]: 2021-09-12 09:17:18 Age [y:d:h:m:s]: 03:144:16:35:00
Block: 332208 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 878677 RingCT/type: yes/0
Extra: 0177282f4433714486427d4964f7f1ef8a35b9213b0a1217eac09bcbe6df0de8f7021100000014fdc024ec000000000000000000

1 output(s) for total of 48.669561480000 dcy

stealth address amount amount idx
00: b6719de8f0a43cad8408c76ccfc7331516372d8b16e4c5b9cc43f228d3b57a9e 48.669561480000 686125 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": 332218, "vin": [ { "gen": { "height": 332208 } } ], "vout": [ { "amount": 48669561480, "target": { "key": "b6719de8f0a43cad8408c76ccfc7331516372d8b16e4c5b9cc43f228d3b57a9e" } } ], "extra": [ 1, 119, 40, 47, 68, 51, 113, 68, 134, 66, 125, 73, 100, 247, 241, 239, 138, 53, 185, 33, 59, 10, 18, 23, 234, 192, 155, 203, 230, 223, 13, 232, 247, 2, 17, 0, 0, 0, 20, 253, 192, 36, 236, 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