Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: aa704a4cf1a6473b0be5c917aa8341999ffb55079a0bab0159178a4ca127e5b9

Tx prefix hash: b1c72bd516f588e24f5c928a1e38326ae310ebb3010570b30c51f4561de732d0
Tx public key: eca5e077fbcec7746551242fccbccb28429355f1076b2322d818fdeabde9f410
Timestamp: 1577711359 Timestamp [UCT]: 2019-12-30 13:09:19 Age [y:d:h:m:s]: 05:036:21:32:31
Block: 35043 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1176103 RingCT/type: yes/0
Extra: 01eca5e077fbcec7746551242fccbccb28429355f1076b2322d818fdeabde9f410021100000009d81c26c0000000000000000000

1 output(s) for total of 469.773861659000 dcy

stealth address amount amount idx
00: 3fe2a1a7686af7a6ff4f275fb8fac520d101329df1c4b939db6b0fa985792dd0 469.773861659000 59036 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": 35053, "vin": [ { "gen": { "height": 35043 } } ], "vout": [ { "amount": 469773861659, "target": { "key": "3fe2a1a7686af7a6ff4f275fb8fac520d101329df1c4b939db6b0fa985792dd0" } } ], "extra": [ 1, 236, 165, 224, 119, 251, 206, 199, 116, 101, 81, 36, 47, 204, 188, 203, 40, 66, 147, 85, 241, 7, 107, 35, 34, 216, 24, 253, 234, 189, 233, 244, 16, 2, 17, 0, 0, 0, 9, 216, 28, 38, 192, 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