Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f3a5aaffe43acf9539efee7e48fa221593d39fd8b4fbcf082aed4727f572a5d6

Tx prefix hash: 7de5166ae737a5c31aba24e40783fcbb6c6b6d4f17d6b2f36372ec8a0800d22a
Tx public key: b39b09f40916f6374ac8c0635f050b86f6fd5531519a4a0d9fc42d216f7314dd
Timestamp: 1577803580 Timestamp [UCT]: 2019-12-31 14:46:20 Age [y:d:h:m:s]: 04:330:23:41:46
Block: 35846 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1125616 RingCT/type: yes/0
Extra: 01b39b09f40916f6374ac8c0635f050b86f6fd5531519a4a0d9fc42d216f7314dd0211000000034ac5aa02000000000000000000

1 output(s) for total of 466.904624366000 dcy

stealth address amount amount idx
00: 7f58789a60c35ee10febdb30b162d07148a48acd7e3c3d5a9d3f701b4991289e 466.904624366000 60509 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": 35856, "vin": [ { "gen": { "height": 35846 } } ], "vout": [ { "amount": 466904624366, "target": { "key": "7f58789a60c35ee10febdb30b162d07148a48acd7e3c3d5a9d3f701b4991289e" } } ], "extra": [ 1, 179, 155, 9, 244, 9, 22, 246, 55, 74, 200, 192, 99, 95, 5, 11, 134, 246, 253, 85, 49, 81, 154, 74, 13, 159, 196, 45, 33, 111, 115, 20, 221, 2, 17, 0, 0, 0, 3, 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