Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fcb9a6a1a2b35453cab733284e70cbc68fbaa6ff5a568ce9095bda4d08f76563

Tx prefix hash: a32e30fafff6787c411acbfe019236c1daf2e6da5115c8bb4e367bcb598eaefb
Tx public key: 2a13ba7c036328027a85c1e72584eed08882f668f12f98a993ab60e31a3a6d11
Timestamp: 1587791221 Timestamp [UCT]: 2020-04-25 05:07:01 Age [y:d:h:m:s]: 04:206:15:25:10
Block: 96091 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1059095 RingCT/type: yes/0
Extra: 012a13ba7c036328027a85c1e72584eed08882f668f12f98a993ab60e31a3a6d1102110000000f4943cd9f000000000000000000

1 output(s) for total of 294.879867286000 dcy

stealth address amount amount idx
00: b7552551a9fa3a187eb525714670adbf3b14970567c8121f7e08d139572c8a56 294.879867286000 170512 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": 96101, "vin": [ { "gen": { "height": 96091 } } ], "vout": [ { "amount": 294879867286, "target": { "key": "b7552551a9fa3a187eb525714670adbf3b14970567c8121f7e08d139572c8a56" } } ], "extra": [ 1, 42, 19, 186, 124, 3, 99, 40, 2, 122, 133, 193, 231, 37, 132, 238, 208, 136, 130, 246, 104, 241, 47, 152, 169, 147, 171, 96, 227, 26, 58, 109, 17, 2, 17, 0, 0, 0, 15, 73, 67, 205, 159, 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