Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6b87cb4c909307e40736b10cf80dd6a717a8e35b0c7786b6ccec63c053b1b04b

Tx prefix hash: ebd93ff01ba985ea4e652cb55cab1cde175e602b2225ddcb1617cdbd9397f386
Tx public key: 2f10949bbecc5d04392f6c136cec0aa683abb902793aed0d8dd3f60b8fe5273d
Timestamp: 1694261202 Timestamp [UCT]: 2023-09-09 12:06:42 Age [y:d:h:m:s]: 01:168:04:46:28
Block: 844349 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 381277 RingCT/type: yes/0
Extra: 012f10949bbecc5d04392f6c136cec0aa683abb902793aed0d8dd3f60b8fe5273d02110000000b4b8f5122000000000000000000

1 output(s) for total of 0.977960518000 dcy

stealth address amount amount idx
00: 005c79e810da3e5196b3a59b30c4864a5dea428186a20b48ec67095a65f56486 0.977960518000 1297651 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": 844359, "vin": [ { "gen": { "height": 844349 } } ], "vout": [ { "amount": 977960518, "target": { "key": "005c79e810da3e5196b3a59b30c4864a5dea428186a20b48ec67095a65f56486" } } ], "extra": [ 1, 47, 16, 148, 155, 190, 204, 93, 4, 57, 47, 108, 19, 108, 236, 10, 166, 131, 171, 185, 2, 121, 58, 237, 13, 141, 211, 246, 11, 143, 229, 39, 61, 2, 17, 0, 0, 0, 11, 75, 143, 81, 34, 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