Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5015abc131d63e17881cc75a64b74cfcbc8f204dc6aee2256c3a28b34f808b4e

Tx prefix hash: 70f16ef324be4686e34f77a94e63665bbe27cf13f1f4d51c13d199298febe7ee
Tx public key: 33b12b187f861b65a42e25d20a2c50eeee037479a31ccd8cff231da4f4611e74
Timestamp: 1578888083 Timestamp [UCT]: 2020-01-13 04:01:23 Age [y:d:h:m:s]: 04:350:10:41:12
Block: 44350 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1140011 RingCT/type: yes/0
Extra: 0133b12b187f861b65a42e25d20a2c50eeee037479a31ccd8cff231da4f4611e7402110000000f4ac5aa02000000000000000000

1 output(s) for total of 437.573367000000 dcy

stealth address amount amount idx
00: 9fee500052a7b7d08bfc6703aab09fb78d614fee832740d1e2a752dc2dfb6e5d 437.573367000000 80683 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": 44360, "vin": [ { "gen": { "height": 44350 } } ], "vout": [ { "amount": 437573367000, "target": { "key": "9fee500052a7b7d08bfc6703aab09fb78d614fee832740d1e2a752dc2dfb6e5d" } } ], "extra": [ 1, 51, 177, 43, 24, 127, 134, 27, 101, 164, 46, 37, 210, 10, 44, 80, 238, 238, 3, 116, 121, 163, 28, 205, 140, 255, 35, 29, 164, 244, 97, 30, 116, 2, 17, 0, 0, 0, 15, 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