Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6846d3abfe9e867347228b74f5759b19d4f20138c8015473c842a926a0848139

Tx prefix hash: b86309ad11b08f4f3f57a9110e49e50d418fed91c1f01de66e2ccfb840679dff
Tx public key: 28c61b9f256d017e94de8332110da051325a9e7ce2da68e6bd2185ae82d38b2d
Timestamp: 1581124894 Timestamp [UCT]: 2020-02-08 01:21:34 Age [y:d:h:m:s]: 04:272:09:05:52
Block: 60797 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1086232 RingCT/type: yes/0
Extra: 0128c61b9f256d017e94de8332110da051325a9e7ce2da68e6bd2185ae82d38b2d0211000000294ac5aa02000000000000000000

1 output(s) for total of 385.971393729000 dcy

stealth address amount amount idx
00: d52ced6bc306ce53f1cf2c540ccdb4161f1eab02d6f5647019e3ca02aca63aa9 385.971393729000 111984 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": 60807, "vin": [ { "gen": { "height": 60797 } } ], "vout": [ { "amount": 385971393729, "target": { "key": "d52ced6bc306ce53f1cf2c540ccdb4161f1eab02d6f5647019e3ca02aca63aa9" } } ], "extra": [ 1, 40, 198, 27, 159, 37, 109, 1, 126, 148, 222, 131, 50, 17, 13, 160, 81, 50, 90, 158, 124, 226, 218, 104, 230, 189, 33, 133, 174, 130, 211, 139, 45, 2, 17, 0, 0, 0, 41, 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