Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7f7e7fb160cebe043ef66d3e030bcacd2e7ecbc4a57b6d7bf1be205d946347ca

Tx prefix hash: ac33d1c742d26ef0c8012148215833b54cd90dac730ca646b3dbfb61d4c55a66
Tx public key: 0c6fd23032eb6ef83e37cc62dd69ce3c49b21bc155a23e5cac1c93ca6e09e1da
Timestamp: 1722780787 Timestamp [UCT]: 2024-08-04 14:13:07 Age [y:d:h:m:s]: 00:245:07:49:02
Block: 1080601 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 175225 RingCT/type: yes/0
Extra: 010c6fd23032eb6ef83e37cc62dd69ce3c49b21bc155a23e5cac1c93ca6e09e1da02110000000891e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4b6f50704b36f1aecad5b1918657ae6c889c2e5e805baf48c94012be4e63da04 0.600000000000 1554032 of 15

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": 1080611, "vin": [ { "gen": { "height": 1080601 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4b6f50704b36f1aecad5b1918657ae6c889c2e5e805baf48c94012be4e63da04" } } ], "extra": [ 1, 12, 111, 210, 48, 50, 235, 110, 248, 62, 55, 204, 98, 221, 105, 206, 60, 73, 178, 27, 193, 85, 162, 62, 92, 172, 28, 147, 202, 110, 9, 225, 218, 2, 17, 0, 0, 0, 8, 145, 225, 60, 4, 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