Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 03ff207b7511af531bfcfda7d6ad93f5ffa1a285a9de28ccd3d474d02444cf2f

Tx prefix hash: ee6ca2b1fd6266ac431307286698a4d8aaa7c06f1d6ea64ac66070dc52b68aaf
Tx public key: 487ec8a4943b63c120fd8e303d04b35cb5c5f67b902f5b264fe1fada76cc2d1a
Timestamp: 1657006860 Timestamp [UCT]: 2022-07-05 07:41:00 Age [y:d:h:m:s]: 02:184:20:38:48
Block: 537014 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 653488 RingCT/type: yes/0
Extra: 01487ec8a4943b63c120fd8e303d04b35cb5c5f67b902f5b264fe1fada76cc2d1a0211000000114da16a3a000000000000000000

1 output(s) for total of 10.201166691000 dcy

stealth address amount amount idx
00: d13a5d1b6093c91c6de761a429e8f72a31d47983af2e3ce114194df2fb4d509c 10.201166691000 966855 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": 537024, "vin": [ { "gen": { "height": 537014 } } ], "vout": [ { "amount": 10201166691, "target": { "key": "d13a5d1b6093c91c6de761a429e8f72a31d47983af2e3ce114194df2fb4d509c" } } ], "extra": [ 1, 72, 126, 200, 164, 148, 59, 99, 193, 32, 253, 142, 48, 61, 4, 179, 92, 181, 197, 246, 123, 144, 47, 91, 38, 79, 225, 250, 218, 118, 204, 45, 26, 2, 17, 0, 0, 0, 17, 77, 161, 106, 58, 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