Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 90fc008e5b03f74c44b2d9cd827da56825767659219207ac3389eba8450c539e

Tx prefix hash: b5d9d558a81df29df458e222d2fdd83d9482f55eb4bf08c92404850e99541df8
Tx public key: c8886f75e2454ae5f396e0ff40cf9de943c6062f36e34ea6d469cf249aca1f5d
Timestamp: 1653730983 Timestamp [UCT]: 2022-05-28 09:43:03 Age [y:d:h:m:s]: 02:326:05:09:17
Block: 510645 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 753570 RingCT/type: yes/0
Extra: 01c8886f75e2454ae5f396e0ff40cf9de943c6062f36e34ea6d469cf249aca1f5d02110000000175e3f0e9000000000000000000

1 output(s) for total of 12.474447687000 dcy

stealth address amount amount idx
00: ba34c3b6ced0e993fa1c437901228d732d67497906a51137052597e2627ad643 12.474447687000 936998 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": 510655, "vin": [ { "gen": { "height": 510645 } } ], "vout": [ { "amount": 12474447687, "target": { "key": "ba34c3b6ced0e993fa1c437901228d732d67497906a51137052597e2627ad643" } } ], "extra": [ 1, 200, 136, 111, 117, 226, 69, 74, 229, 243, 150, 224, 255, 64, 207, 157, 233, 67, 198, 6, 47, 54, 227, 78, 166, 212, 105, 207, 36, 154, 202, 31, 93, 2, 17, 0, 0, 0, 1, 117, 227, 240, 233, 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