Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 52df9a39f5e1ff49b969524d8ea0ff509570cfede6b69e8ef0ef627eba43b64d

Tx prefix hash: 0a453e542af1cfa7531f6161c38182aeb1fbbace9ba6b4d0640bec504d37f33b
Tx public key: 805df7f06fd1af0c7fca1713aba57f0f3f2805cd8cf091dfd840c44808d052bf
Timestamp: 1577765578 Timestamp [UCT]: 2019-12-31 04:12:58 Age [y:d:h:m:s]: 05:065:08:23:18
Block: 35459 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1196497 RingCT/type: yes/0
Extra: 01805df7f06fd1af0c7fca1713aba57f0f3f2805cd8cf091dfd840c44808d052bf02110000000e4ac5aa02000000000000000000

1 output(s) for total of 468.295388053000 dcy

stealth address amount amount idx
00: 74f42e520ca0c622dfb168c1bea5fc87b76bff61a327ff1594515fa21a8d53d0 468.295388053000 59816 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": 35469, "vin": [ { "gen": { "height": 35459 } } ], "vout": [ { "amount": 468295388053, "target": { "key": "74f42e520ca0c622dfb168c1bea5fc87b76bff61a327ff1594515fa21a8d53d0" } } ], "extra": [ 1, 128, 93, 247, 240, 111, 209, 175, 12, 127, 202, 23, 19, 171, 165, 127, 15, 63, 40, 5, 205, 140, 240, 145, 223, 216, 64, 196, 72, 8, 208, 82, 191, 2, 17, 0, 0, 0, 14, 74, 197, 170, 2, 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