Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3ede6cb1edb901c1328e3d367c680eb317281023078032d45e82ddc3cf778be5

Tx prefix hash: d26b9da120b75e648d1eb721d5de2d19db8cef256356b60189c9fa0932f93e58
Tx public key: a8e62c17bd57a7defddc66e5fdde13db08e55c36ea2513d32400651efb7f244e
Timestamp: 1576425644 Timestamp [UCT]: 2019-12-15 16:00:44 Age [y:d:h:m:s]: 05:125:17:04:30
Block: 27566 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1236472 RingCT/type: yes/0
Extra: 01a8e62c17bd57a7defddc66e5fdde13db08e55c36ea2513d32400651efb7f244e0211000000639159db1e000000000000000000

1 output(s) for total of 497.351308247000 dcy

stealth address amount amount idx
00: 2cb4c75003bed8f138d67230a49ca952d010091814b836e324ed8e8c7e12fbfb 497.351308247000 45578 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": 27576, "vin": [ { "gen": { "height": 27566 } } ], "vout": [ { "amount": 497351308247, "target": { "key": "2cb4c75003bed8f138d67230a49ca952d010091814b836e324ed8e8c7e12fbfb" } } ], "extra": [ 1, 168, 230, 44, 23, 189, 87, 167, 222, 253, 220, 102, 229, 253, 222, 19, 219, 8, 229, 92, 54, 234, 37, 19, 211, 36, 0, 101, 30, 251, 127, 36, 78, 2, 17, 0, 0, 0, 99, 145, 89, 219, 30, 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